@jest/test-result

What is @jest/test-result?

The @jest/test-result package is part of the Jest testing framework, primarily used to handle and represent the results of tests. It provides structures and utility functions to process and display the outcomes of test suites and individual tests.

What are @jest/test-result's main functionalities?

Create a test result

This feature allows developers to create a structured test result object, which includes the number of passing, failing, and pending tests, along with detailed results for each test.

{
  "numFailingTests": 0,
  "numPassingTests": 3,
  "numPendingTests": 0,
  "testResults": [
    {
      "fullName": "adds 1 + 2 to equal 3",
      "status": "passed"
    }
  ]
}

Summarize test results

This utility function summarizes the test results, providing a quick overview of the test suite's outcome. It's useful for generating reports or logs.

const { summarizeResults } = require('@jest/test-result');
const testResults = {
  numFailingTests: 1,
  numPassingTests: 2,
  numPendingTests: 1,
  testResults: [
    { fullName: 'test1', status: 'passed' },
    { fullName: 'test2', status: 'failed' },
    { fullName: 'test3', status: 'pending' }
  ]
};
console.log(summarizeResults(testResults));

Other packages similar to @jest/test-result

mocha

Mocha is a feature-rich JavaScript test framework running on Node.js and in the browser, making asynchronous testing simple and fun. Mocha tests run serially, allowing for flexible and accurate reporting, while mapping uncaught exceptions to the correct test cases. It is similar to @jest/test-result in that it handles test results but is a more comprehensive testing solution.

chai

Chai is a BDD / TDD assertion library for node and the browser that can be delightfully paired with any javascript testing framework. It's similar to @jest/test-result in terms of being used in testing environments but focuses more on assertions rather than handling test results.

README

The README file is missing

Changelog

26.6.2

Features

• [jest-core] Add findRelatedTests and nonFlagArgs in allowed config options for updateConfigAndRun in watch plugins (#10659)

Fixes

• [babel-plugin-jest-hoist] Preserve order of hoisted mock nodes within containing block (#10536)
• [babel-plugin-jest-hoist] Hoist pure constants to support experimental JSX transform in hoisted mocks (#10723)
• [babel-preset-jest] Update babel-preset-current-node-syntax to support top level await (#10747)
• [expect] Revert "Fix objectContaining to work recursively into sub-objects (#10508)" (#10766)
• [jest-circus, jest-jasmine2] fix: don't assume stack is always a string (#10697)
• [jest-config] Fix bug introduced in watch mode by PR #10678 (#10692)
• [jest-config] Throw correct error for missing preset modules (#10737)
• [jest-resolve-dependencies] Resolve mocks as dependencies (#10713)
• [jest-runtime] Handle file URLs in dynamic imports (#10744)
• [jest-runtime, babel-jest] Pass more ESM options to @jest/transform (#10752)
• [jest-runtime] Properly inject extraGlobals into the runtime (#10758)
• [jest-transform] Link to ESM docs on syntax errors (#10748)

Chore & Maintenance

• [docs] Add docs for using mocks in TypeScript (#10415)
• [eslint-config-fb-strict] Move package from this repo to fbjs repo (#10739)
• [examples] Update TypeScript example to show use of newer Jest types (#10399)
• [jest-cli] chore: standardize files and folder names (#10698)
• [jest-config] Switch ts-node Register type to Service due to deprecation (#11210)